Description

For quite some time now, the macos and ios CI test runners have been exiting with exit code 1 with the following: https://github.com/firebase/flutterfire/actions/runs/16416732379/job/46384578343?pr=17541#step:16:383

Two tests were silently crashing app, one of the crashes has been fixed: https://github.com/firebase/flutterfire/pull/17440/files#diff-021dfe6df9eae0b2a7c718fd0df578115005602e6e476dece7e0b2a67139d7cbR255

The other crash is a mystery, I could not reproduce running example app with the exact same code, therefore I have opted to skip for apple platforms: https://github.com/firebase/flutterfire/pull/17440/files#diff-dd4162c32c7a0146e8a9c7874e8642422e51160833ff49eea64c852b8b215ef9R879

Related Issues

Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (melos run analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• I signed the CLA.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change.
• No, this is not a breaking change.